Skip to content

Conversation

@mpenick
Copy link
Contributor

@mpenick mpenick commented Mar 29, 2021

Latency-aware policy update timer wasn't started on request processors.

Latency-aware policy update timer wasn't started on request processors.
@mpenick
Copy link
Contributor Author

mpenick commented Mar 29, 2021

Also, tested manually by running a query against a three node cluster then causing an artificial delay using traffic control:

tc qdisc add dev lo root handle 1: prio
tc qdisc add dev lo parent 1:3 handle 30: netem delay 1ms 
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 \
   match ip dst 127.0.0.2 flowid 1:3

Watch logs for:

1617039588.003 [TRACE] (latency_aware_policy.cpp:105:virtual datastax::internal::core::Host::Ptr datastax::internal::core::LatencyAwarePolicy::LatencyAwareQueryPlan::compute_next()): Skipping 127.0.0.2 because latency is too high 4.312233

@mpenick mpenick merged commit ca4a2cd into master Mar 29, 2021
fsaporito pushed a commit to cloudian/cpp-driver that referenced this pull request May 9, 2023
Latency-aware policy update timer wasn't started on request processors.
@absurdfarce absurdfarce deleted the fix-latency-aware branch October 10, 2025 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant